Selection of a scheduling user equipment

ABSTRACT

Apparatuses, methods, and systems are disclosed for selection of a scheduling user equipment. One embodiment of a computer-readable storage device storing machine readable code, when executed by a processor, cause the processor to receive first information from a plurality of user equipments, wherein the first information indicates at least one sidelink user equipment in communication with each user equipment of the plurality of user equipments. In some embodiments, the code further causes the processor to select a scheduling user equipment from the plurality of user equipments based on a quality of a first connection interface and a second connection interface of each user equipment of the plurality of user equipments indicated in the first information. In some embodiments, the code further causes the processor to transition to a fallback mode in response to mode 2d resource allocation being unavailable and occurrence of a radio link failure or a handover.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation Application of U.S. patentapplication Ser. No. 16/816,001 filed on Mar. 11, 2020, which claimspriority to U.S. patent application Ser. No. 62/822,133 entitled“EFFICIENT RESOURCE SCHEDULING FOR V2X RESOURCE ALLOCATION MODE 2DOPERATION PROCEDURES” and filed on Mar. 22, 2019 for KarthikeyanGanesan, which are incorporated herein by reference in their entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to selection of ascheduling user equipment.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”), Authentication,Authorization, and Accounting (“AAA”), Positive-Acknowledgment (“ACK”),Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”),Access and Mobility Management Function (“AMF”), Angle of Arrival(“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Access Stratum(“AS”), Authentication Server Function (“AUSF”), Authentication Token(“AUTN”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”),Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer StatusReport (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI(“C-RNTI”), Carrier Aggregation (“CA”), Contention-Based Random Access(“CBRA”), Clear Channel Assessment (“CCA”), Common Control Channel(“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity(“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”),Contention-Free Random Access (“CFRA”), Closed-Loop (“CL”), CoordinatedMultipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix(“CP”), Cyclical Redundancy Check (“CRC”), Channel State Information(“CSI”), Channel State Information-Reference Signal (“CSI-RS”), CommonSearch Space (“CSS”), Control Resource Set (“CORESET”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data RadioBearer (“DRB”), Discontinuous Reception (“DRX”), Downlink Pilot TimeSlot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), EnhancedMobile Broadband (“eMBB”), Evolved Node B (“eNB”), ExtensibleAuthentication Protocol (“EAP”), Effective Isotropic Radiated Power(“EIRP”), European Telecommunications Standards Institute (“ETSI”),Frame Based Equipment (“FBE”), Frequency Division Duplex (“FDD”),Frequency Division Multiplexing (“FDM”), Frequency Division MultipleAccess (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”),Frequency Range 1—sub 6 GHz frequency bands and/or 410 MHz to 7125 MHz(“FR1”), Frequency Range 2—24.25 GHz to 52.6 GHz (“FR2”), UniversalGeographical Area Description (“GAD”), Group Leader (“GL”), 5G Node B orNext Generation Node B (“gNB”), Global Navigation Satellite System(“GNSS”), General Packet Radio Services (“GPRS”), Guard Period (“GP”),Global Positioning System (“GPS”), Global System for MobileCommunications (“GSM”), Globally Unique Temporary UE Identifier(“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”),Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”),Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”),Identity or Identifier (“ID”), Information Element (“IE”), InternationalMobile Equipment Identity (“IMEI”), International Mobile SubscriberIdentity (“IMSI”), International Mobile Telecommunications (“IMT”),Internet-of-Things (“IoT”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3(“L3”), Licensed Assisted Access (“LAA”), Local Area Network (“LAN”),Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), LogicalChannel (“LCH”), Logical Channel Prioritization (“LCP”), Log-LikelihoodRatio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”),Medium Access Control (“MAC”), Multimedia Broadcast Multicast Services(“MBMS”), Modulation Coding Scheme (“MCS”), Master Information Block(“MIB”), Multiple Input Multiple Output (“MIMO”), Mobility Management(“MM”), Mobility Management Entity (“MME”), Mobile Network Operator(“MNO”), massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), MachineType Communication (“MTC”), Multi User Shared Access (“MUSA”), NonAccess Stratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment(“NACK”) or (“NAK”), Network Entity (“NE”), Network Function (“NF”),Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-OrthogonalMultiple Access (“NOMA”), New Radio (“NR”), NR Unlicensed (“NR-U”),Network Repository Function (“NRF”), Network Slice Instance (“NSI”),Network Slice Selection Assistance Information (“NSSAI”), Network SliceSelection Function (“NSSF”), Network Slice Selection Policy (“NSSP”),Operation, Administration, and Maintenance System or Operation andMaintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing(“OFDM”), Open-Loop (“OL”), Other System Information (“OSI”), PowerAngular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), PowerControl (“PC”), UE to UE interface (“PC5”), Primary Cell (“PCell”),Policy Control Function (“PCF”), Physical Cell Identity (“PCP”),Physical Downlink Control Channel (“PDCCH”), Packet Data ConvergenceProtocol (“PDCP”), Packet Data Network Gateway (“PGW”), PhysicalDownlink Shared Channel (“PDSCH”), Pattern Division Multiple Access(“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”),Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), PhysicalRandom Access Channel (“PRACH”), Physical Resource Block (“PRB”),Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel(“PSCCH”), Primary Secondary Cell (“PSCell”), Physical Sidelink FeedbackControl Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), Quasi Co-Located (“QCL”),Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”),Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network(“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Random AccessProcedure (“RACH”), Random Access Preamble Identifier (“RAPID”), RandomAccess Response (“RAR”), Resource Element Group (“REG”), Radio LinkControl (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC UnacknowledgedMode/Transparent Mode (“RLC-UM/TM”), Radio Link Failure (“RLF”), RadioLink Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”),Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”),Radio Resource Control (“RRC”), Radio Resource Management (“RRM”),Resource Spread Multiple Access (“RSMA”), Reference Signal ReceivedPower (“RSRP”), Received Signal Strength Indicator (“RSSI”), Round TripTime (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”),Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), SingleCarrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell(“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCK”),Sidelink Control Information (“SCP”), Sub-carrier Spacing (“SCS”),Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), SidelinkFeedback Content Information (“SFCI”), Serving Gateway (“SGW”), SystemInformation Block (“SIB”), SystemInformationBlockType1 (“SIB1”),SystemInformationBlockType2 (“SIB2”), Subscriber Identity/IdentificationModule (“SIM”), Signal-to-Interference-Plus-Noise Ratio (“SINR”),Sidelink (“SL”), Service Level Agreement (“SLA”), SidelinkSynchronization Signals (“SLSS”), Session Management Function (“SMF”),Special Cell (“SpCell”), Single Network Slice Selection AssistanceInformation (“S-NSSAI”), Scheduling Request (“SR”), Signaling RadioBearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”),Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI RS”), SidelinkPRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block(“SSB”), Subscription Concealed Identifier (“SUCI”), Scheduling UserEquipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber PermanentIdentifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TAUpdate (“TAU”), Timing Alignment Timer (“TAT”), Transport Block (“TB”),Transport Block Size (“TB S”), Time-Division Duplex (“TDD”), TimeDivision Multiplex (“TDM”), Time Division Orthogonal Cover Code(“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time ofFlight (“ToF”), Transmission Power Control (“TPC”), TransmissionReception Point (“TRP”), Transmission Time Interval (“TTI”), Transmit(“TX”), Uplink Control Information (“UCI”), Unified Data ManagementFunction (“UDM”), Unified Data Repository (“UDR”), User Entity/Equipment(Mobile Terminal) (“UE”), Uplink (“UL”), UL SCH (“UL-SCH”), UniversalMobile Telecommunications System (“UMTS”), User Plane (“UP”), UPFunction (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Ultra-reliabilityand Low-latency Communications (“URLLC”), UE Route Selection Policy(“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Anything (“V2X”),Visiting AMF (“vAMF”), Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”),Wide Area Network (“WAN”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”).

In certain wireless communications networks, a user equipment may beused for scheduling.

BRIEF SUMMARY

Methods for selection of a scheduling user equipment are disclosed.Apparatuses and systems also perform the functions of the methods. Oneembodiment of a computer-readable storage device storing machinereadable code, when executed by a processor, cause the processor toreceive first information from a plurality of user equipments, whereinthe first information indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments. In some embodiments, the code further causes the processorto select a scheduling user equipment from the plurality of userequipments based on a quality of a first connection interface and asecond connection interface of each user equipment of the plurality ofuser equipments indicated in the first information. In some embodiments,the code further causes the processor to transition to a fallback modein response to mode 2d resource allocation being unavailable andoccurrence of a radio link failure or a handover.

One apparatus for selection of a scheduling user equipment includes areceiver that receives first information from a plurality of userequipments, wherein the first information indicates at least onesidelink user equipment in communication with each user equipment of theplurality of user equipments. In certain embodiments, the apparatusincludes a processor that selects a scheduling user equipment from theplurality of user equipments based on a quality of a first connectioninterface and a second connection interface of each user equipment ofthe plurality of user equipments indicated in the first information. Theprocessor transitions to a fallback mode in response to mode 2d resourceallocation being unavailable and occurrence of a radio link failure or ahandover.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for selection of a scheduling userequipment;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used as a scheduling user equipment;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for selection of a scheduling user equipment;and

FIG. 4 is a flow chart diagram illustrating one embodiment of a methodfor selection of a scheduling user equipment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forselection of a scheduling user equipment. In one embodiment, thewireless communication system 100 includes remote units 102 and networkunits 104. Even though a specific number of remote units 102 and networkunits 104 are depicted in FIG. 1 , one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. In certain embodiments,the remote units 102 may communicate directly with other remote units102 via sidelink communication.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In various embodiments, a network unit 104 may receive first informationfrom a plurality of user equipments (e.g., remote units 102), whereinthe first information indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments. In some embodiments, the network unit 104 may select ascheduling user equipment from the plurality of user equipments based ona quality of a first connection interface and a second connectioninterface of each user equipment of the plurality of user equipmentsindicated in the first information. Accordingly, the network unit 104may be used for selection of a scheduling user equipment.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used as ascheduling user equipment. The apparatus 200 includes one embodiment ofthe remote unit 102. Furthermore, the remote unit 102 may include aprocessor 202, a memory 204, an input device 206, a display 208, atransmitter 210, and a receiver 212. In some embodiments, the inputdevice 206 and the display 208 are combined into a single device, suchas a touchscreen. In certain embodiments, the remote unit 102 may notinclude any input device 206 and/or display 208. In various embodiments,the remote unit 102 may include one or more of the processor 202, thememory 204, the transmitter 210, and the receiver 212, and may notinclude the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein.

In some embodiments, the transmitter 210 may transmit messages to otherremote units 102. Although only one transmitter 210 and one receiver 212are illustrated, the remote unit 102 may have any suitable number oftransmitters 210 and receivers 212. The transmitter 210 and the receiver212 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 210 and the receiver 212 may be part of atransceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forselection of a scheduling user equipment. The apparatus 300 includes oneembodiment of the network unit 104. Furthermore, the network unit 104may include a processor 302, a memory 304, an input device 306, adisplay 308, a transmitter 310, and a receiver 312. As may beappreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In various embodiments, the receiver 312 may receive first informationfrom a plurality of user equipments, wherein the first informationindicates at least one sidelink user equipment in communication witheach user equipment of the plurality of user equipments. In certainembodiments, the processor 302 may select a scheduling user equipmentfrom the plurality of user equipments based on a quality of a firstconnection interface and a second connection interface of each userequipment of the plurality of user equipments indicated in the firstinformation.

Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

In some embodiments, V2X resource allocation may be based on mode 2doperational procedures in a physical layer (e.g., such as an interestindication to become SUE, selection of SUE, creating neighbor list basedon L1 measurement or SL positioning, resource allocation, and fall backoperational modes). In such embodiments, an application layer may not beaware of a radio link quality of a UE and may not select the rightscheduling UE for a group. Moreover, in such embodiments, a BS may beinvolved to choose the SUE in a selection procedure.

In certain embodiments, there may be two SL resource allocation modes:mode 1 in which a BS schedules SL resources to be used by a UE for SLtransmissions; and mode 2 in which the UE determines (e.g., BS does notschedule) SL transmission resources within SL resources configured bythe BS, the network, or pre-configured SL resources.

In various embodiments, the definition of SL resource allocation mode 2may cover: a) a UE autonomously selects SL resource for transmission; b)the UE assists SL resource selection for other UEs; c) the UE isconfigured with NR configured grant (e.g., type-1 like) for SLtransmission; and/or d) the UE schedules SL transmissions of other UEs.

In some embodiments, in the context of mode-2(d), NR V2X may support thefollowing functionality: a) a UE informs a gNB about group members andthe gNB provides individual resource pool configuration and/orindividual resource configuration through the same UE to each groupmember UE within the same group—it may not require connection betweenthe member UE and the gNB; b) the UE cannot modify the configurationprovided by the gNB; c) higher layer signaling may be used to provideconfiguration—no physical layer signaling is used; d) one or bothresource pool configurations and resource configuration may besupported; and/or e) functionality defined as a part of mode-2 mayapplicable for this feature. As may be appreciated, functionalitiesdescribed herein may be up to UE capabilities.

In certain embodiments, such as for group-based SL communication, a UE-Amay inform its serving gNB about members UE-B, UE-C, and so on of agroup, and the gNB may provide individual resource pool configurationsand/or individual resource configurations to each group member throughUE-A. In such embodiments, the UE-A cannot modify the configurations,and there is no direct connection required between any member UE and thegNB. Higher-layer only signaling may be used to provide theconfigurations, and such functionality may be up to UE capabilities.

As used herein, the term eNB and/or gNB may be used for a base station,but it may be replaceable by any other radio access node (e.g., BS, eNB,gNB, AP, NR, and so forth). Furthermore, various methods may bedescribed in the context of 5G NR; however, the methods may be equallyapplicable to other mobile communication systems supporting servingcells and/or carriers configured for sidelink communication over a PC5interface.

In various embodiments, a V2X transmitting UE may periodically receiveand/or decode SCI from other neighboring UEs and the SCI content mayinclude information about a source ID, a destination ID, and/or a groupID. In some embodiments, V2X group formation may happen in two ways: 1)the group is semi statically formed based on a layer 2 ID or in anapplication layer for a particular session based application (e.g.,platooning, etc.); and 2) the group is dynamically configured based on acertain communication range.

In certain embodiments, every V2X UE may be aware of neighbor UEs thatmay be its group members. In such embodiments, the V2X UE may createand/or maintain one or more neighbor lists for each layer 2 group ID orapplication ID based on a SL L1 RSRP and/or RSSI measured from a PSCCHDMRS.

In various embodiments, as part of an SUE selection process criteria,UEs may nominate themselves for the role of SUE by transmitting aninterest indication to a gNB. In such embodiments, if there are manyinterested UEs, as part of the selection process, the gNB may select anSUE based on the quality of the UE's Uu and/or PC5 connection (e.g.,determined by measuring a SL RSRP of group members) in which the qualityis above a corresponding threshold.

In some embodiments, as part of interest indication signaling to a gNBabout a UE's intention to become an SUE, the UE may transmit additionalinformation such as a group ID, a number of group members identifiedthat may be included in a neighbor list, a number of active transmittersthat may be part of the group members, a minimum QoS and/or a maximumQoS range for the group members, a degree of automation of the groupmembers (e.g., may be low degree of automation to a higher and/orhighest degree of automation that may indirectly relate to a latencyand/or a reliability requirement of the group members), a transmit rateof a message, a message size, a cast type, and so forth. In suchembodiments, the interest indication signaling from the UE to the gNBmay be made using RRC signaling, using MAC CE signaling, using L1signaling, with the combination of additional information, as part of aUE assistance report, and/or as part of a measurement report. Moreover,in such embodiments, either the gNB provides a SL L1 RSRP and/or RSSIthreshold for group member identification to the UE or the gNB filtersthe group members shared by the interested UE based on the RSRP and/orRSSI threshold and/or required communication range provided by a higherlayer.

In one embodiment, a UE may share a neighbor cell list and/or a numberof neighboring group members with or without a PC5 link quality with aBS as and when required (e.g., for an SUE seeking resources to schedulegroup members, a member UE indicating interest in becoming the SUEetc.). In certain embodiments, a BS may explicitly ask about a UEsbelonging to a certain group, a certain geographical area, and/or acommunication range to transmit interest indication. In someembodiments, UEs (e.g., based on a UE capability) may include one ormore features (e.g., relay ability, a higher number of antennas for Uuand/or SL, a high transmit power, a capability to form multiple beams,and/or a car capability such a height of the car, a high batterycapacity, and so forth) with a transmission of an interest indication toa BS. In various embodiments, an SUE may report member UEs within aminimum communication range indicated by upper layers and/or may reportactive member UEs within the minimum communication range. As usedherein, active member UEs may mean group member with potential V2Xmessage transmission requirements.

In certain embodiments, a sidelink positioning method may be used todetermine group members within a certain communication range. With theSL positioning method, a TX UE may determine a location of RX UEs in agroup or information from which the location of RX UEs may be inferred.The information used to infer the location of RX UEs may be globallocation coordinates of RX UEs or some relative positioning informationthat may be based on a time of arrival, flight measurements, spatialmeasurements, and/or angular measurements (e.g., AoA, AoD) from a latestreceived transmission from the TX UE.

In some embodiments, RX UEs may be configured to report either time ofarrival, AoA, and/or AoD measurements from a configured set of RSs, andthe RSs may be either S-SSB, S-CSI RS, or S-PRS transmissions from a TXUE. A TX UE may perform beam sweeping transmission of RSs from multipleantenna panels and may indicate to report a relative positioningmeasurement report in SCI. In one embodiment, an RX UE reports a beam IDand a relative positioning report to a TX UE. A number of beams used fortransmission of RSs may be different for different antenna panels (e.g.,depending on a size of the antenna panels—number of antenna elements,directivity and/or launch angles capability of the antenna panels,and/or placement of the antenna panels on the vehicle). In variousembodiments, a resource set that includes a RS resource identifier and asequence ID configured for beam sweeping transmission may be indicatedin SCI by a TX UE using a groupcast or broadcast transmission. Incertain embodiments, RX UEs report a beam index of a strongest receivedRS and a Tx UE maps the index of the strongest received RS beam to abeam direction. The beam direction may be used to calculate an AoD. Insome embodiments, an RX UE may report a ToF and/or an AoA to a TX UE. Afeedback resource and/or a feedback timing for a RX UE may besemi-statically or dynamically configured either by a TX UE or by a BS.

In various embodiments, a gNB determines (e.g., selects) an SUE based ona radio link quality in Uu and/or PC5 as part of a selection process. Insuch embodiments, a number of member UE that may be identified by an SUEmay be more compared to other UE's in the group. In certain embodiments,after a gNB receives an interest indication signaling an interest of aUE to become an SUE, the gNB checks whether mode 2d operation is enabledto operate in its cellular area, in its geographical area, and/or basedon availability of resources. If mode 2d operation is not enabled, thenthe gNB may transmit a reject message to the UE and, if there are notenough resources available, the gNB may inform the UE to transmit therequest after a certain period of time. If the mode 2d operation isenable, then the gNB transmits information indicating selection of theSUE to its group member either via unicast or multicast signaling withadditional information (e.g., UE ID of the SUE, common resourcesallocated for the group members and/or resource allocated to each memberof the group, a cast type allowed, a flag to indicate whether member UEsare enabled to perform a sensing operation to select resources, longterm and/or short term sensing needed by the group members to select theresource from the common resource, validity of the resources,communication range of the SUE, fallback operational mode due tomobility event, fallback SL carrier frequency, and/or resource pools).In some embodiments, signaling to member UEs may be done directly by agNB (e.g., to in-coverage UEs and/or RRC connected UEs) and/or via theselected SUE (e.g., to out of coverage UEs, RRC idle UEs, or UEs inneighboring cells—since the SUE may not be aware of the Uu state of themembers, it makes a groupcast transmission). In certain embodiments, agNB notifies an SUE using one or more of RRC signaling, MAC CEsignaling, and/or SCI signaling. In various embodiments, a gNB mayindicate using a flag either in RRC, MIB, and/or SIB's whether or notmode 2d operation is enabled. In some embodiments, an SUE may use agroupcast transmission in PC5 RRC, PSBCH, PSCCH, and/or PSSCH to relay amessage to group members. In certain embodiments, an SUE may use a beamsweeping transmission and/or groupcast HARQ ACK/NACK feedback tofacilitate reception by group members. In various embodiments, adedicated resource provided by a gNB to each group member may be relayedby an SUE with a PC5 unicast transmission either with PC5 RRC, PSSCH,PSCCH, and/or MAC CE. In some embodiments, a fallback operational modeand resource pools may be indicate by a gNB in one SIB message.

In certain embodiments, a resource selection method of a group member ona common resource could may depend on a validity of the resourceprovided by a gNB or an SUE. If a validity of a resource is less than along term sensing window size, then a UE autonomously uses a short termsensing and/or random selection on common resources. In suchembodiments, either the gNB or the SUE may provide information aboutshort term sensing parameters (e.g., threshold, sensing window, PSSCHtime and/or frequency location in a common resource pool). In variousembodiments, a gNB or an SUE may provide a time and frequency locationof PSCCH in a resource pool and a DMRS configuration (e.g., with anassumption that the PSCCH and PSSCH are located in the same resourcepool). In such embodiments, the member UE may use this information abouta PSCCH-DMRS to perform short term energy sensing within a configuredsensing window and to determine whether or not a resource is availablefor transmission. In some embodiments, if a gNB or an SUE providesmultiple patterns and/or configured grant type 1 (e.g., a pattern isdefined by a size and positions of a resource in time and frequency, anda number of resources) for group members to select via groupcast orunicast signaling (e.g., via SCI, MAC CE, and/or PC5 RRC), then thegroup members perform short term energy sensing on a PSSCH-DMRS toselect an unused pattern. As may be appreciated, each pattern may usethe same configured DMRS location; otherwise, if a location of the DMRSin each pattern is different, it may be signaled to the group memberUEs. In certain embodiments, the SUE may configure a sidelink mode ofoperation of group members via groupcast or unicast signaling that maybe based on SCI, MAC CE, and/or PC5 RRC. In various embodiments, asidelink sub mode may include sidelink dynamic scheduling by a SUE. Theoperation procedure of this submode may be similar to mode 1 resourceallocation. The concept of SR/BSR to request resources and transmit thebuffer status report may be used for this submode. A new sidelinkphysical channel may be used to carry SR, BSR, PHR, and/or a powercontrol command may be defined for information exchange between the SUEand group member. The power control command may be indicated in SFCI,PSFCH, PSCCH, and/or PSSCH. In some embodiments, an SUE may transmit aconfiguration of configured grant type 1 and/or configured grant type 2like resources to each group member UE via groupcast or unicastsignaling and activation and/or deactivation messages via SCI, MAC CE,and/or an SCI format. The SCI format may be defined for any SUEprocedure described herein.

In certain embodiments, a gNB (e.g., besides choosing an SUE) may choosea candidate SUE or a candidate SUE list based on an interest indicationmessage received from one or more UEs. The gNB may inform group membersof the candidate SUE list. The candidate SUE list may be periodicallyevaluated and refreshed based on a radio link quality of a Uu and/or aPC5 (e.g., the PC5 radio link quality may be based on a neighbormeasurement that may be either RSRP or positioning based). If the linkquality of a candidate SUE is better than a serving SUE, then the gNBmay reselect an SUE. In various embodiments, monitoring a link qualitymay include a Uu quality of the RRC connected candidate SUEs and/or aPC5 link quality of candidate UEs with their identified group members.

In some embodiments, there may be a fall back operational mode due to amobility event such as RLF and/or handover. If a mode 2d based resourceallocation is not available, then the fallback operational mode is used.The fallback operational mode enables fallback to any other schedulingmethods including mode-1, mode-2 (e.g., any mode 2 sub modes), and/orpreconfigured resource pools with or without a sensing operation.

In various embodiments, for a radio link failure of an SUE with respectto a gNB, either the gNB may reselect an SUE from a candidate list as anext serving SUE, or, because the SUE is aware of the candidate SUElist, the SUE may groupcast to the candidate SUEs about the SUEsimpending radio link failure. Each candidate SUE may evaluate linkquality with respect to the gNB and then groupcast to the group memberswith its UE ID is to become the serving SUE. In one embodiment, if thereis more than one candidate SUE, then a candidate SUE is selected thathas a maximum number of identified group member UEs.

In certain embodiments, if one group member UE or SUE initiates ahandover, then a serving gNB may signal permission in a handover commandas part of UE context information for mode 2d operation in a target gNBwith additional information such as a number of active transmitters, aQoS, resource requirements, and so forth. If the target gNB accepts ahandover request and provides new resources from its cell, then theserving gNB may inform the SUE and/or group member UEs of theconfiguration of the target gNB. If mode 2d operation is not possible inthe target gNB and/or the target gNB does not have enough resources,then the source gNB may switch the group to a fallback operational mode,such as mode 1, mode 2a, or mode 2c. In some embodiments, an SUE mayinform group members about a change in an operation mode via sidelinksignaling that may be SCI, MAC CE, and/or PC5 RRC. If SCI is used, a bitfield may be used to indicate a mode and/or a specific SCI format may beused to distinguish each mode.

In some embodiments, an SUE selection may be based on a PC5 link qualitywith its neighboring UEs. The neighboring UEs may be sync ref UEs, orany other UEs in a group, in a certain geographical area, and/or basedon identified group members from its neighbor. In one embodiment, a UEacting as a sync ref UE (e.g., providing sidelink timing information toa group of UEs) or any other UEs may explicitly transmit a requestmessage via group cast PSCCH to transmit a SL RSRP and/or RSSImeasurement based on a configured RS which could be S-SSB, S-CSI RS,S-DMRS-PSCCH, and/or SL positioning. In certain embodiments, a UE maytransmit an interest indication to other neighboring UEs via sidelinkgroupcast or broadcast transmission with various parameters via PC5 RRC,MAC CE, PDCP control, SCI, and so forth.

In various embodiments, resource selection by an SUE may be carried by asensing operation that may include receiving and/or decoding SCI onindicated resource pools. In some embodiments, in an SCI transmission toother UEs, an SUE may indicate a group ID (e.g., layer 1 group ID, layer2 group ID, etc.) in a source ID field and/or required resources (e.g.,in terms of resource pools, validity period of the resources, and soforth). The SUE may also indicate a priority value in a QoS prioritythat indicates to other UEs that the resources are reserved for mode 2doperations. In certain embodiments, an SCI format may be used toindicate mode 2d operations to other UEs. In some embodiments, only anSUE in a group may sense and reserve resources on behalf of groupmembers.

In some embodiments, SUE selection is based on a quality of a Uu and/ora PC5 connection (e.g., obtained by measuring a SL RSRP of groupmembers) being above a corresponding threshold.

In certain embodiments, an SUE may create a neighbor list for eachdestination group (e.g., corresponding to a L2 ID or an applicationlayer group ID) based on SL RSRP and/or SL positioning.

In various embodiments, a UE may share a neighbor cell list and/or anumber of neighboring group members with or without a PC5 link qualitywith a BS as and when required (e.g., for an SUE seeking resources toschedule group members, for a member UE indicating interest in becomingthe SUE, and so forth).

In some embodiments, a gNB selects an SUE and notifies group membersusing a L2 ID of the selected SUE. In such embodiments, additionalparameters may also be signaled, such as allowed cast types, duration ofresource pool validity, and so forth. Signaling member UEs may be donedirectly by a gNB (e.g., to in-coverage and/or RRC connected UEs) and/orvia a selected SUE (e.g., to out of coverage UEs, RRC idle UEs, and/orUEs in neighboring cells). Because the SUE may not be aware of a Uustate of member UEs, the SUE may make a groupcast transmission.

In certain embodiments, a gNB may keep a candidate SUE list and maycontinuously monitor a link quality of the candidate SUE. This may leadto reselection of an SUE.

In various embodiments, monitoring link quality may include a Uu qualityof RRC connected candidate SUEs and/or a PC5 link quality of thecandidate SUEs with their identified group members.

In some embodiments, there may be a fall back operational mode due to amobility event such as RLF and/or handover. In such embodiments, if amode 2d based resource allocation is not available, then a fallbackoperational mode may be used thereby enabling fallback to any otherscheduling method including mode-1, mode-2, and/or preconfiguredresource pools with or without a sensing operation.

In certain embodiments, an SUE reports member UEs that are within aminimum communication range indicated by upper layers and/or reportsactive member UEs that are within the minimum communication range. Asmay be appreciated, active member UEs may mean group member withpotential V2X message transmission requirements.

FIG. 4 is a flow chart diagram illustrating one embodiment of a method400 for selection of a scheduling user equipment. In some embodiments,the method 400 is performed by an apparatus, such as the network unit104. In certain embodiments, the method 400 may be performed by aprocessor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 400 may include receiving 402 first information from aplurality of user equipments, wherein the first information indicates atleast one sidelink user equipment in communication with each userequipment of the plurality of user equipments. In some embodiments, themethod 400 includes selecting 404 a scheduling user equipment from theplurality of user equipments based on a quality of a first connectioninterface and a second connection interface of each user equipment ofthe plurality of user equipments indicated in the first information.

In certain embodiments, the first connection interface comprises aninterface between a user equipment and a network device. In someembodiments, the second connection interface comprises an interfacebetween a first user equipment and a second user equipment. In variousembodiments, the scheduling user equipment is selected from theplurality of user equipments in response to a first quality of the firstconnection interface being greater than a first threshold and a secondquality of the second connection interface being greater than a secondthreshold.

In one embodiment, the quality of the first connection interface and thesecond connection interface is determined by measuring a sidelinkreference signal received power. In certain embodiments, the firstinformation is determined based on sidelink reference signal receivedpower, sidelink positioning, or a combination thereof.

In some embodiments, the sidelink positioning is determined based on aglobal positioning location or a relative position. In variousembodiments, the relative position is based on a time of arrival, a timeof flight, a spatial measurement, an angular measurement, an angle ofarrival, an angle of arrival, or some combination thereof. In oneembodiment, the method 400 further comprises transmitting secondinformation indicating the scheduling user equipment.

In certain embodiments, the second information is transmitted viaunicast or multicast signaling. In some embodiments, the secondinformation comprises a user equipment identifier corresponding to thescheduling user equipment, an allocation of a common resource, anallocation of a user equipment specific resource, an allowed cast type,a sensing operation indication, sensing information corresponding to thecommon resource, a validity of the common resource, a scheduling userequipment communication range, a fallback operation mode, a fallbacksidelink carrier frequency, a fallback sidelink resource pool, or somecombination thereof. In various embodiments, the second informationcomprises short term sensing parameters, a time and frequency locationof a sidelink control channel in a resource pool, a demodulationreference signal configuration, or some combination thereof.

In one embodiment, the short term sensing parameters comprise athreshold, a sensing window, a time and frequency location of a sidelinkcontrol channel in a resource pool, or some combination thereof. Incertain embodiments, the method 400 further comprises receiving updatedfirst information from the plurality of user equipments. In someembodiments, the method 400 further comprises reselecting the schedulinguser equipment from the plurality of user equipments based on theupdated first information.

In various embodiments, the method 400 further comprises transitioningto a fall back mode in response to mode 2d resource allocation beingunavailable and occurrence of a radio link failure or a handover. In oneembodiment, the fall back mode comprises a mode 1, a mode 2, aconfigured resource pool, a preconfigured resource pool, or somecombination thereof. In certain embodiments, the scheduling userequipment indicates a group identifier, resource pool resources, apriority value, or some combination thereof to one or more sidelink userequipments.

In one embodiment, a method comprises:

receiving first information from a plurality of user equipments, whereinthe first information indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments; and

selecting a scheduling user equipment from the plurality of userequipments based on a quality of a first connection interface and asecond connection interface of each user equipment of the plurality ofuser equipments indicated in the first information.

In certain embodiments, the first connection interface comprises aninterface between a user equipment and a network device.

In some embodiments, the second connection interface comprises aninterface between a first user equipment and a second user equipment.

In various embodiments, the scheduling user equipment is selected fromthe plurality of user equipments in response to a first quality of thefirst connection interface being greater than a first threshold and asecond quality of the second connection interface being greater than asecond threshold.

In one embodiment, the quality of the first connection interface and thesecond connection interface is determined by measuring a sidelinkreference signal received power.

In certain embodiments, the first information is determined based onsidelink reference signal received power, sidelink positioning, or acombination thereof.

In some embodiments, the sidelink positioning is determined based on aglobal positioning location or a relative position.

In various embodiments, the relative position is based on a time ofarrival, a time of flight, a spatial measurement, an angularmeasurement, an angle of arrival, an angle of arrival, or somecombination thereof.

In one embodiment, the method further comprises transmitting secondinformation indicating the scheduling user equipment.

In certain embodiments, the second information is transmitted viaunicast or multicast signaling.

In some embodiments, the second information comprises a user equipmentidentifier corresponding to the scheduling user equipment, an allocationof a common resource, an allocation of a user equipment specificresource, an allowed cast type, a sensing operation indication, sensinginformation corresponding to the common resource, a validity of thecommon resource, a scheduling user equipment communication range, afallback operation mode, a fallback sidelink carrier frequency, afallback sidelink resource pool, or some combination thereof.

In various embodiments, the second information comprises short termsensing parameters, a time and frequency location of a sidelink controlchannel in a resource pool, a demodulation reference signalconfiguration, or some combination thereof.

In one embodiment, the short term sensing parameters comprise athreshold, a sensing window, a time and frequency location of a sidelinkcontrol channel in a resource pool, or some combination thereof.

In certain embodiments, the method further comprises receiving updatedfirst information from the plurality of user equipments.

In some embodiments, the method further comprises reselecting thescheduling user equipment from the plurality of user equipments based onthe updated first information.

In various embodiments, the method further comprises transitioning to afall back mode in response to mode 2d resource allocation beingunavailable and occurrence of a radio link failure or a handover.

In one embodiment, the fall back mode comprises a mode 1, a mode 2, aconfigured resource pool, a preconfigured resource pool, or somecombination thereof.

In certain embodiments, the scheduling user equipment indicates a groupidentifier, resource pool resources, a priority value, or somecombination thereof to one or more sidelink user equipments.

In one embodiment, an apparatus comprises: a receiver that receivesfirst information from a plurality of user equipments, wherein the firstinformation indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments; and a processor that selects a scheduling user equipmentfrom the plurality of user equipments based on a quality of a firstconnection interface and a second connection interface of each userequipment of the plurality of user equipments indicated in the firstinformation.

In certain embodiments, the first connection interface comprises aninterface between a user equipment and a network device.

In some embodiments, the second connection interface comprises aninterface between a first user equipment and a second user equipment.

In various embodiments, the scheduling user equipment is selected fromthe plurality of user equipments in response to a first quality of thefirst connection interface being greater than a first threshold and asecond quality of the second connection interface being greater than asecond threshold.

In one embodiment, the quality of the first connection interface and thesecond connection interface is determined by measuring a sidelinkreference signal received power.

In certain embodiments, the first information is determined based onsidelink reference signal received power, sidelink positioning, or acombination thereof.

In some embodiments, the sidelink positioning is determined based on aglobal positioning location or a relative position.

In various embodiments, the relative position is based on a time ofarrival, a time of flight, a spatial measurement, an angularmeasurement, an angle of arrival, an angle of arrival, or somecombination thereof.

In one embodiment, the apparatus further comprises a transmitter thattransmits second information indicating the scheduling user equipment.

In certain embodiments, the second information is transmitted viaunicast or multicast signaling.

In some embodiments, the second information comprises a user equipmentidentifier corresponding to the scheduling user equipment, an allocationof a common resource, an allocation of a user equipment specificresource, an allowed cast type, a sensing operation indication, sensinginformation corresponding to the common resource, a validity of thecommon resource, a scheduling user equipment communication range, afallback operation mode, a fallback sidelink carrier frequency, afallback sidelink resource pool, or some combination thereof.

In various embodiments, the second information comprises short termsensing parameters, a time and frequency location of a sidelink controlchannel in a resource pool, a demodulation reference signalconfiguration, or some combination thereof.

In one embodiment, the short term sensing parameters comprise athreshold, a sensing window, a time and frequency location of a sidelinkcontrol channel in a resource pool, or some combination thereof.

In certain embodiments, the receiver receives updated first informationfrom the plurality of user equipments.

In some embodiments, the processor reselects the scheduling userequipment from the plurality of user equipments based on the updatedfirst information.

In various embodiments, the processor transitions to a fall back mode inresponse to mode 2d resource allocation being unavailable and occurrenceof a radio link failure or a handover.

In one embodiment, the fall back mode comprises a mode 1, a mode 2, aconfigured resource pool, a preconfigured resource pool, or somecombination thereof.

In certain embodiments, the scheduling user equipment indicates a groupidentifier, resource pool resources, a priority value, or somecombination thereof to one or more sidelink user equipments.

In one embodiment, a computer readable storage device storing machinereadable code, when executed by a processor, cause the processor toreceive first information from a plurality of user equipments, whereinthe first information indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments, select a scheduling user equipment from the plurality ofuser equipments based on a quality of a first connection interface and asecond connection interface of each user equipment of the plurality ofuser equipments indicated in the first information, and transition to afallback mode in response to mode 2d resource allocation beingunavailable and occurrence of a radio link failure or a handover.

In certain embodiments, the code further causes to select the schedulinguser equipment selected from the plurality of user equipments inresponse to a first quality of the first connection interface beinggreater than a first threshold and a second quality of the secondconnection interface being greater than a second threshold.

In certain embodiments, the code further causes to determine the qualityof the first connection interface and the second connection interface bymeasuring a sidelink reference signal received power.

In certain embodiments, the code further causes to determine the firstinformation based on sidelink reference signal received power, sidelinkpositioning, or a combination thereof.

In certain embodiments, the code further causes to determine thesidelink positioning based on a global positioning location or arelative position.

In certain embodiments, the relative position is based on a time ofarrival, a time of flight, a spatial measurement, an angularmeasurement, an angle of arrival, or some combination thereof.

In certain embodiments, the code further causes to transmit secondinformation indicating the scheduling user equipment.

In certain embodiments, the second information comprises a userequipment identifier corresponding to the scheduling user equipment, anallocation of a common resource, an allocation of a user equipmentspecific resource, an allowed cast type, a sensing operation indication,sensing information corresponding to the common resource, a validity ofthe common resource, a scheduling user equipment communication range, afallback operation mode, a fallback sidelink carrier frequency, afallback sidelink resource pool, or some combination thereof.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprises: a receiver thatreceives first information from a plurality of user equipments, whereinthe first information indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments; and a processor that selects a scheduling user equipmentfrom the plurality of user equipments based on a quality of a firstconnection interface and a second connection interface of each userequipment of the plurality of user equipments indicated in the firstinformation; and transitions to a fallback mode in response to mode 2dresource allocation being unavailable and occurrence of a radio linkfailure or a handover, wherein the first connection interface comprisesan interface between a user equipment and a network device, wherein thesecond connection interface comprises an interface between a first userequipment and a second user equipment.
 2. The apparatus of claim 1,wherein the scheduling user equipment is selected from the plurality ofuser equipments in response to a first quality of the first connectioninterface being greater than a first threshold and a second quality ofthe second connection interface being greater than a second threshold.3. The apparatus of claim 1, wherein the quality of the first connectioninterface and the second connection interface is determined by measuringa sidelink reference signal received power.
 4. The apparatus of claim 1,wherein the first information is determined based on sidelink referencesignal received power, sidelink positioning, or a combination thereof.5. The apparatus of claim 4, the sidelink positioning is determinedbased on a global positioning location or a relative position.
 6. Theapparatus of claim 5, wherein the relative position is based on a timeof arrival, a time of flight, a spatial measurement, an angularmeasurement, an angle of arrival, an angle of arrival, or somecombination thereof.
 7. The apparatus of claim 1, wherein the apparatusfurther comprises a transmitter that transmits second informationindicating the scheduling user equipment.
 8. The apparatus of claim 7,wherein the second information is transmitted via unicast or multicastsignaling.
 9. The apparatus of claim 7, wherein the second informationcomprises a user equipment identifier corresponding to the schedulinguser equipment, an allocation of a common resource, an allocation of auser equipment specific resource, an allowed cast type, a sensingoperation indication, sensing information corresponding to the commonresource, a validity of the common resource, a scheduling user equipmentcommunication range, a fallback operation mode, a fallback sidelinkcarrier frequency, a fallback sidelink resource pool, or somecombination thereof.
 10. The apparatus of claim 7, wherein the secondinformation comprises short term sensing parameters, a time andfrequency location of a sidelink control channel in a resource pool, ademodulation reference signal configuration, or some combinationthereof.
 11. The apparatus of claim 10, wherein the short term sensingparameters comprise a threshold, a sensing window, a time and frequencylocation of a sidelink control channel in a resource pool, or somecombination thereof.
 12. The apparatus of claim 1, wherein the receiverreceives updated first information from the plurality of userequipments.
 13. The apparatus of claim 12, wherein the processorreselects the scheduling user equipment from the plurality of userequipments based on the updated first information.
 14. The apparatus ofclaim 1, wherein the fallback mode comprises a mode 1, a mode 2, aconfigured resource pool, a preconfigured resource pool, or somecombination thereof.
 15. The apparatus of claim 1, wherein thescheduling user equipment indicates a group identifier, resource poolresources, a priority value, or some combination thereof to one or moresidelink user equipments.
 16. A method comprising: receiving firstinformation from a plurality of user equipments, wherein the firstinformation indicates at least one sidelink user equipment incommunication with each user equipment of the plurality of userequipments; selecting a scheduling user equipment from the plurality ofuser equipments based on a quality of a first connection interface and asecond connection interface of each user equipment of the plurality ofuser equipments indicated in the first information; and transitioning toa fall back mode in response to mode 2d resource allocation beingunavailable and occurrence of a radio link failure or a handover,wherein the first connection interface comprises an interface between auser equipment and a network device, wherein the second connectioninterface comprises an interface between a first user equipment and asecond user equipment.
 17. The method of claim 16, wherein thescheduling user equipment is selected from the plurality of userequipments in response to a first quality of the first connectioninterface being greater than a first threshold and a second quality ofthe second connection interface being greater than a second threshold.18. The method of claim 16, wherein the quality of the first connectioninterface and the second connection interface is determined by measuringa sidelink reference signal received power.
 19. The method of claim 16,wherein the first information is determined based on sidelink referencesignal received power, sidelink positioning, or a combination thereof,wherein the sidelink positioning is determined based on a globalpositioning location or a relative position, wherein the relativeposition is based on a time of arrival, a time of flight, a spatialmeasurement, an angular measurement, an angle of arrival, or somecombination thereof.
 20. The method of claim 16, further comprisingtransmitting second information indicating the scheduling userequipment.